OpenEdge Development:<br />Progress Dynamics Administration Running the DCU in batch mode

You can run the DCU in batch mode and completely unattended. This facility allows you to provide an automated application installation or upgrade procedure for end-user sites where technical knowledge might be limited. This also allows you to install/upgrade applications in environments without access to a GUI client/server license, such as for sites running WebSpeed-only clients.

For creating a batch-mode DCU procedure, Progress Dynamics provides three components:

User interface — This is the standard DCU GUI that you run with additional command-line parameters. The GUI runs exactly like the full-interactive DCU, except instead of configuring Dynamics (updating the Repository), the additional parameters direct the DCU to store all of the configuration data that you enter in XML files that you specify for use with the DCU batch procedure.

Phase 1 configuration — This is the first DCU batch component, consisting of a Progress 4GL procedure (dcuphase1.p) that uses the XML files you generate from the user interface component. This batch component updates the Repository schema and executes various fix programs.

Phase 2 configuration — The is the second DCU batch component, consisting of a Progress 4GL procedure (dcuphase2.p). This batch component completes the same Repository update procedure that the full-interactive DCU initiates after logging into the Progress Dynamics environment as an admin user.

Run the DCU GUI to generate the batch-mode XML data files.

Create a script that executes dcuphase1.p and dcuphase2.p in sequence, and performs any other actions that you require to complete the application installation or upgrade.